Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ed3ffe943db1d658cfc3eb8273328e86e9d233e3198e2da4e2555689baf17ab

Tx prefix hash: 384fd35ab08940cb51df75670e27e188593a2b6a7d6cd51890f1dfc0271eb9e3
Tx public key: 70e10b0a4d8c041aec4e87134576f9111e6a0a7de1081043c0a10215b43bc043
Timestamp: 1577650893 Timestamp [UCT]: 2019-12-29 20:21:33 Age [y:d:h:m:s]: 05:066:09:10:58
Block: 34533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197203 RingCT/type: yes/0
Extra: 0170e10b0a4d8c041aec4e87134576f9111e6a0a7de1081043c0a10215b43bc0430211000000024ac5aa02000000000000000000

1 output(s) for total of 471.605315387000 dcy

stealth address amount amount idx
00: 9187508fcefb1d006e7da521a5770cf8d85b3aac919d4af91269c08b83a04ba7 471.605315387000 58129 of 0

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": 34543, "vin": [ { "gen": { "height": 34533 } } ], "vout": [ { "amount": 471605315387, "target": { "key": "9187508fcefb1d006e7da521a5770cf8d85b3aac919d4af91269c08b83a04ba7" } } ], "extra": [ 1, 112, 225, 11, 10, 77, 140, 4, 26, 236, 78, 135, 19, 69, 118, 249, 17, 30, 106, 10, 125, 225, 8, 16, 67, 192, 161, 2, 21, 180, 59, 192, 67, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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