Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e02729f50956c513905d36e24632b94c7ef588b72bed6c5a78b3514c852a788e

Tx prefix hash: c1c51850393a9f72f0e87c52cb892237c9b2530d9699fa4562f3e88a47542aeb
Tx public key: ce2d134d948e7dee6a4ce157a3fe1c8cbb80b8ecdadc0a07db35fc018686c9d0
Timestamp: 1728945287 Timestamp [UCT]: 2024-10-14 22:34:47 Age [y:d:h:m:s]: 00:175:14:48:46
Block: 1131718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125284 RingCT/type: yes/0
Extra: 01ce2d134d948e7dee6a4ce157a3fe1c8cbb80b8ecdadc0a07db35fc018686c9d0021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5373f78308cf02f5fe4c0f455546ca914f70d72518aed881df1681b3385f0dcd 0.600000000000 1614623 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": 1131728, "vin": [ { "gen": { "height": 1131718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5373f78308cf02f5fe4c0f455546ca914f70d72518aed881df1681b3385f0dcd" } } ], "extra": [ 1, 206, 45, 19, 77, 148, 142, 125, 238, 106, 76, 225, 87, 163, 254, 28, 140, 187, 128, 184, 236, 218, 220, 10, 7, 219, 53, 252, 1, 134, 134, 201, 208, 2, 17, 0, 0, 0, 2, 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