Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 809951c3cb6b07116c1eb5aa744db0eacd0eb305b2e78347741e40ad237857b2

Tx prefix hash: 0e518986137eaaf36ea9193ca6407d0bb423f890b51723e28c716591c2bf7945
Tx public key: f12502368d42bc9ba7f2a5374a04c145307807bca268f39a703fb878ba8a6068
Timestamp: 1728967246 Timestamp [UCT]: 2024-10-15 04:40:46 Age [y:d:h:m:s]: 00:040:06:27:38
Block: 1131899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28744 RingCT/type: yes/0
Extra: 01f12502368d42bc9ba7f2a5374a04c145307807bca268f39a703fb878ba8a6068021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fae9c8f5a663a2fe1b4d3f3c52eea3d3e9984a446aea4abd4a483d5227b993c 0.600000000000 1614808 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": 1131909, "vin": [ { "gen": { "height": 1131899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fae9c8f5a663a2fe1b4d3f3c52eea3d3e9984a446aea4abd4a483d5227b993c" } } ], "extra": [ 1, 241, 37, 2, 54, 141, 66, 188, 155, 167, 242, 165, 55, 74, 4, 193, 69, 48, 120, 7, 188, 162, 104, 243, 154, 112, 63, 184, 120, 186, 138, 96, 104, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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