Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c3c76d262202f26ccbc191a18ccfc68eb1a614f1bf9d3625e526476e2be7ad4

Tx prefix hash: 69ac210a5e8f8ee06c93d633e38a06646b87e204b9a0c370ccd13771a524907d
Tx public key: c4d8eaa1c74187585b2f4eafa237257ca528e07bcd302182628e1ae8863b4fb0
Timestamp: 1648343475 Timestamp [UCT]: 2022-03-27 01:11:15 Age [y:d:h:m:s]: 03:219:11:51:56
Block: 467142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 934801 RingCT/type: yes/0
Extra: 01c4d8eaa1c74187585b2f4eafa237257ca528e07bcd302182628e1ae8863b4fb0021100000009bf7ee4e7000000000000000000

1 output(s) for total of 17.384607416000 dcy

stealth address amount amount idx
00: 0fb73abe72e7ae71f32d3d56dfdd1080f02cf0c5358f5c8307c816df2174b643 17.384607416000 885593 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": 467152, "vin": [ { "gen": { "height": 467142 } } ], "vout": [ { "amount": 17384607416, "target": { "key": "0fb73abe72e7ae71f32d3d56dfdd1080f02cf0c5358f5c8307c816df2174b643" } } ], "extra": [ 1, 196, 216, 234, 161, 199, 65, 135, 88, 91, 47, 78, 175, 162, 55, 37, 124, 165, 40, 224, 123, 205, 48, 33, 130, 98, 142, 26, 232, 134, 59, 79, 176, 2, 17, 0, 0, 0, 9, 191, 126, 228, 231, 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