Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc76c5abab5be3dde2ac3d655feacf4ab5f256d150e25aa76e1c66d42a67a261

Tx prefix hash: 45873c18c8be620391bade96a414b926e63c18bf37a0bef58458cffda5a26c8e
Tx public key: 1d356b7060efb613a97f3cc3d9edc56ad3cf2ef4ca7ec6bdd1e5e733022f2f66
Timestamp: 1723717846 Timestamp [UCT]: 2024-08-15 10:30:46 Age [y:d:h:m:s]: 00:283:08:24:45
Block: 1088378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202427 RingCT/type: yes/0
Extra: 011d356b7060efb613a97f3cc3d9edc56ad3cf2ef4ca7ec6bdd1e5e733022f2f66021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5128286c16dc4aa747d145aee9df86e0356dc211ae092a9f70d7d5017c2ebaad 0.600000000000 1562993 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": 1088388, "vin": [ { "gen": { "height": 1088378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5128286c16dc4aa747d145aee9df86e0356dc211ae092a9f70d7d5017c2ebaad" } } ], "extra": [ 1, 29, 53, 107, 112, 96, 239, 182, 19, 169, 127, 60, 195, 217, 237, 197, 106, 211, 207, 46, 244, 202, 126, 198, 189, 209, 229, 231, 51, 2, 47, 47, 102, 2, 17, 0, 0, 0, 4, 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