Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 646d56a2efce0d8536c0113713b72c33cb20241bf8b02a01e6a1f7902132db5f

Tx prefix hash: 535a90410b5ffdfa1c0012b937f465b43875b9cecb7b18457d582b405871e867
Tx public key: f092433a08356212c4787e3f6818106a3e4ce83a4dd2b664315c09ee36345d8a
Timestamp: 1713072113 Timestamp [UCT]: 2024-04-14 05:21:53 Age [y:d:h:m:s]: 00:215:06:19:31
Block: 1000100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154119 RingCT/type: yes/0
Extra: 01f092433a08356212c4787e3f6818106a3e4ce83a4dd2b664315c09ee36345d8a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bbc26c440c161d1764d81baf27157ff24441ea1269612bccb6748f0aeaef5a7 0.600000000000 1460590 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": 1000110, "vin": [ { "gen": { "height": 1000100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bbc26c440c161d1764d81baf27157ff24441ea1269612bccb6748f0aeaef5a7" } } ], "extra": [ 1, 240, 146, 67, 58, 8, 53, 98, 18, 196, 120, 126, 63, 104, 24, 16, 106, 62, 76, 232, 58, 77, 210, 182, 100, 49, 92, 9, 238, 54, 52, 93, 138, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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