Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a1cf2b149bfc0999e4183f8ac223649c6a8ddbaf53d12987f548811f0ba89c3

Tx prefix hash: c4fbd8ba7be4bc24ec2aa08fa3b70f3e1433099f72af189089efce28a8b75fe6
Tx public key: c419cc5a33b67a469fea7e46350761a4fcd8c11944ab68290243b37d7fdc75a9
Timestamp: 1697128636 Timestamp [UCT]: 2023-10-12 16:37:16 Age [y:d:h:m:s]: 01:176:21:46:51
Block: 868157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387441 RingCT/type: yes/0
Extra: 01c419cc5a33b67a469fea7e46350761a4fcd8c11944ab68290243b37d7fdc75a90211000000284b8f5122000000000000000000

1 output(s) for total of 0.815521659000 dcy

stealth address amount amount idx
00: 931f0787014767076203aa86f3073b154f8ec8bed3b7be23ce38a07934cf95f8 0.815521659000 1322930 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": 868167, "vin": [ { "gen": { "height": 868157 } } ], "vout": [ { "amount": 815521659, "target": { "key": "931f0787014767076203aa86f3073b154f8ec8bed3b7be23ce38a07934cf95f8" } } ], "extra": [ 1, 196, 25, 204, 90, 51, 182, 122, 70, 159, 234, 126, 70, 53, 7, 97, 164, 252, 216, 193, 25, 68, 171, 104, 41, 2, 67, 179, 125, 127, 220, 117, 169, 2, 17, 0, 0, 0, 40, 75, 143, 81, 34, 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