Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 799e14af194883f2012ff3f605ee0acfc275b86faf6beb8d7cb6b2d37bd63aee

Tx prefix hash: 6cc3a9959b893ddf3b0813e1cad8a8f3834216173329485cdcbfe0135d911909
Tx public key: d41536525d9e22da198ab4ddd47ae2f9c21ff097712f2ef2ed9fd002f86cae8e
Timestamp: 1727566894 Timestamp [UCT]: 2024-09-28 23:41:34 Age [y:d:h:m:s]: 00:056:18:54:29
Block: 1120291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40575 RingCT/type: yes/0
Extra: 01d41536525d9e22da198ab4ddd47ae2f9c21ff097712f2ef2ed9fd002f86cae8e021100000001e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: fc535b1e863517ca3827517d3a5f16d2e905125a364d9f74b4eb89f3900b2875 0.608000000000 1602152 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1120301, "vin": [ { "gen": { "height": 1120291 } } ], "vout": [ { "amount": 608000000, "target": { "key": "fc535b1e863517ca3827517d3a5f16d2e905125a364d9f74b4eb89f3900b2875" } } ], "extra": [ 1, 212, 21, 54, 82, 93, 158, 34, 218, 25, 138, 180, 221, 212, 122, 226, 249, 194, 31, 240, 151, 113, 47, 46, 242, 237, 159, 208, 2, 248, 108, 174, 142, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8