Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 419fccd896dd6a56afcd39e278999f0bc84f7bfe0a524ed42c7110ee4cc0b045

Tx prefix hash: 99e7964306bc518eced7ce708cf33b7319263485495c296788638b88ed0a63e5
Tx public key: 777b652ea7f0372343c0b580aa65c83fdb2c649ac80700239f5dfdab407c82b4
Timestamp: 1681203257 Timestamp [UCT]: 2023-04-11 08:54:17 Age [y:d:h:m:s]: 01:326:11:32:37
Block: 736144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494615 RingCT/type: yes/0
Extra: 01777b652ea7f0372343c0b580aa65c83fdb2c649ac80700239f5dfdab407c82b40211000000035029cbac000000000000000000

1 output(s) for total of 2.232798664000 dcy

stealth address amount amount idx
00: ff03d7532d31e329ea52baf1152ab5a545e6df6ef6a936d0f2023c88592f55c4 2.232798664000 1182543 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": 736154, "vin": [ { "gen": { "height": 736144 } } ], "vout": [ { "amount": 2232798664, "target": { "key": "ff03d7532d31e329ea52baf1152ab5a545e6df6ef6a936d0f2023c88592f55c4" } } ], "extra": [ 1, 119, 123, 101, 46, 167, 240, 55, 35, 67, 192, 181, 128, 170, 101, 200, 63, 219, 44, 100, 154, 200, 7, 0, 35, 159, 93, 253, 171, 64, 124, 130, 180, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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