Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5a5efa13371f15791612390fa4188588d394ad3bca87c891ebe124e3247d547

Tx prefix hash: 9998558f3b48fcbaef505ff86b208ee630f609d848ee4c6b52b484df0872d1c5
Tx public key: 357aab21d4eb7ffadc73119e8ef55a9c38d5fb47dfac08f9c3f079b3eda9141c
Timestamp: 1701486923 Timestamp [UCT]: 2023-12-02 03:15:23 Age [y:d:h:m:s]: 01:083:12:22:13
Block: 904064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320805 RingCT/type: yes/0
Extra: 01357aab21d4eb7ffadc73119e8ef55a9c38d5fb47dfac08f9c3f079b3eda9141c02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.620098457000 dcy

stealth address amount amount idx
00: 5ff48fb65918c08e1aa189e0efd84c25fc382427c08d6c70138b10aae4f9879c 0.620098457000 1360767 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": 904074, "vin": [ { "gen": { "height": 904064 } } ], "vout": [ { "amount": 620098457, "target": { "key": "5ff48fb65918c08e1aa189e0efd84c25fc382427c08d6c70138b10aae4f9879c" } } ], "extra": [ 1, 53, 122, 171, 33, 212, 235, 127, 250, 220, 115, 17, 158, 142, 245, 90, 156, 56, 213, 251, 71, 223, 172, 8, 249, 195, 240, 121, 179, 237, 169, 20, 28, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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