Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd780e4bd5b96f455c214465a401b997c4f69b926b8ac442452676c521390aae

Tx prefix hash: 6075f6369e352c60ff4c205665db6119f6bc2dd1edd00d976ea3959bff5c0170
Tx public key: 8f5e2770eacb7e123035619dd483254e18aa67f7535d03a4ace1d4362d375b8a
Timestamp: 1731450337 Timestamp [UCT]: 2024-11-12 22:25:37 Age [y:d:h:m:s]: 00:199:23:55:14
Block: 1152391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142812 RingCT/type: yes/0
Extra: 018f5e2770eacb7e123035619dd483254e18aa67f7535d03a4ace1d4362d375b8a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15b6e9eb5c791d33ab1930dccb347c75b864a1d569bb0f5b83e2d4d9ca723ce4 0.600000000000 1637988 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": 1152401, "vin": [ { "gen": { "height": 1152391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15b6e9eb5c791d33ab1930dccb347c75b864a1d569bb0f5b83e2d4d9ca723ce4" } } ], "extra": [ 1, 143, 94, 39, 112, 234, 203, 126, 18, 48, 53, 97, 157, 212, 131, 37, 78, 24, 170, 103, 247, 83, 93, 3, 164, 172, 225, 212, 54, 45, 55, 91, 138, 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