Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f04b4100fb487d0f532ad3561e215e009fbe8c1b21184e11437eb3a1092cb39a

Tx prefix hash: 6300a6ba3fb582137334b5504af14f5982c4cc2acd02c898b1f0d47a76de3ee1
Tx public key: 33b9800d8b713a21a8fc51df21551812ccdeef5af076a80053f263b9173d0a45
Timestamp: 1729588490 Timestamp [UCT]: 2024-10-22 09:14:50 Age [y:d:h:m:s]: 00:142:13:19:28
Block: 1137019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101688 RingCT/type: yes/0
Extra: 0133b9800d8b713a21a8fc51df21551812ccdeef5af076a80053f263b9173d0a45021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41a4b0be2dba5fae2ee0ff93be35db030c7d83b0e69fe58a15ad3a60605173a6 0.600000000000 1620430 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": 1137029, "vin": [ { "gen": { "height": 1137019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41a4b0be2dba5fae2ee0ff93be35db030c7d83b0e69fe58a15ad3a60605173a6" } } ], "extra": [ 1, 51, 185, 128, 13, 139, 113, 58, 33, 168, 252, 81, 223, 33, 85, 24, 18, 204, 222, 239, 90, 240, 118, 168, 0, 83, 242, 99, 185, 23, 61, 10, 69, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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