Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 415ce0616815981d152dac3be6e94dd140dba2029c5acb1b518c66c7ea78f0be

Tx prefix hash: e75b5cf72a92c9f76ea3e47659c0c519346b8b93d2280d77797292c18626871f
Tx public key: ba1b3b83fa604d71e701e0e0ebbf916b3cb2bb338ae54577bb5202a10ca9c09f
Timestamp: 1694911236 Timestamp [UCT]: 2023-09-17 00:40:36 Age [y:d:h:m:s]: 01:166:08:35:26
Block: 849747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379956 RingCT/type: yes/0
Extra: 01ba1b3b83fa604d71e701e0e0ebbf916b3cb2bb338ae54577bb5202a10ca9c09f021100000002faf35c9c000000000000000000

1 output(s) for total of 0.938502641000 dcy

stealth address amount amount idx
00: 8820061489f94aafdd75479444f553c696acbfb3e252fe7efe1ac5de454d10fb 0.938502641000 1303425 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": 849757, "vin": [ { "gen": { "height": 849747 } } ], "vout": [ { "amount": 938502641, "target": { "key": "8820061489f94aafdd75479444f553c696acbfb3e252fe7efe1ac5de454d10fb" } } ], "extra": [ 1, 186, 27, 59, 131, 250, 96, 77, 113, 231, 1, 224, 224, 235, 191, 145, 107, 60, 178, 187, 51, 138, 229, 69, 119, 187, 82, 2, 161, 12, 169, 192, 159, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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