Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e58bfe961b3c093c5a558552ef496831a19d360dbf5f3ebbf0ac31fe2dfa89ec

Tx prefix hash: c2e7ee78160f4c98e805be298668ac2a74209250b68c09b49b919bb741f11f5b
Tx public key: d01eb099361dad7bdf3787d5b52aa8335bb5a14fc468943c5a9eafe2a98de182
Timestamp: 1737165972 Timestamp [UCT]: 2025-01-18 02:06:12 Age [y:d:h:m:s]: 00:305:20:01:45
Block: 1199715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216096 RingCT/type: yes/0
Extra: 01d01eb099361dad7bdf3787d5b52aa8335bb5a14fc468943c5a9eafe2a98de182021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a67a463dc7c7ae4017b6086f97bf624fddb610e3bf9f8b018985d424b8b04a3e 0.600000000000 1686348 of 15

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": 1199725, "vin": [ { "gen": { "height": 1199715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a67a463dc7c7ae4017b6086f97bf624fddb610e3bf9f8b018985d424b8b04a3e" } } ], "extra": [ 1, 208, 30, 176, 153, 54, 29, 173, 123, 223, 55, 135, 213, 181, 42, 168, 51, 91, 181, 161, 79, 196, 104, 148, 60, 90, 158, 175, 226, 169, 141, 225, 130, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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