Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d6bdb4550efbc3382303e179460b5abe47c83e8b5397677dcd27b46a683fc53

Tx prefix hash: 303622eee26d8c1c1423c6c35a56b0f7ed68535488325fa2d4408b40407b024a
Tx public key: 901674fb569bd1bec60d6e593d9b85a97b6e7ff69c5c993a686f6bc0e7decfec
Timestamp: 1740813558 Timestamp [UCT]: 2025-03-01 07:19:18 Age [y:d:h:m:s]: 00:011:10:40:08
Block: 1229646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8207 RingCT/type: yes/0
Extra: 01901674fb569bd1bec60d6e593d9b85a97b6e7ff69c5c993a686f6bc0e7decfec021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d36ed74f5a78fd40e8d0c482d13bfc60d0aa637a846324a1e25d04a443203fd 0.600000000000 1716533 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": 1229656, "vin": [ { "gen": { "height": 1229646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d36ed74f5a78fd40e8d0c482d13bfc60d0aa637a846324a1e25d04a443203fd" } } ], "extra": [ 1, 144, 22, 116, 251, 86, 155, 209, 190, 198, 13, 110, 89, 61, 155, 133, 169, 123, 110, 127, 246, 156, 92, 153, 58, 104, 111, 107, 192, 231, 222, 207, 236, 2, 17, 0, 0, 0, 7, 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