Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f2524fee064683cd5e2fad1f31f03ddb2a78649ab85f4cbfdf9ce945a98b2bc

Tx prefix hash: ecc4f2415339430f00b99b93806a93bd2066809f3ea5662ea8030319aeaf4675
Tx public key: 5c401cf96dac53e58d0a3a2f4d7e4d468796fae5faf2d5c1b8df410eff0ee9c9
Timestamp: 1672954829 Timestamp [UCT]: 2023-01-05 21:40:29 Age [y:d:h:m:s]: 02:026:04:42:54
Block: 668396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540369 RingCT/type: yes/0
Extra: 015c401cf96dac53e58d0a3a2f4d7e4d468796fae5faf2d5c1b8df410eff0ee9c902110000000833af99f4000000000000000000

1 output(s) for total of 3.743919888000 dcy

stealth address amount amount idx
00: 0707cc942cdb15df22443e8c933d4d7cec9fa01efa5a62fa412397dec5f8fc7f 3.743919888000 1109641 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": 668406, "vin": [ { "gen": { "height": 668396 } } ], "vout": [ { "amount": 3743919888, "target": { "key": "0707cc942cdb15df22443e8c933d4d7cec9fa01efa5a62fa412397dec5f8fc7f" } } ], "extra": [ 1, 92, 64, 28, 249, 109, 172, 83, 229, 141, 10, 58, 47, 77, 126, 77, 70, 135, 150, 250, 229, 250, 242, 213, 193, 184, 223, 65, 14, 255, 14, 233, 201, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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