Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f65a7044f0ef0513ce9cfba9233d4841dbed4a2683356f0192b7b272d95a7ef

Tx prefix hash: 5ac30b1e1b531b6c0439a8a2c0683fa4875cf54ec19ca83d73c37412438975ae
Tx public key: 830d0c961058f4bb69c061d910febc1aa5cfe4c504eda8047e949a083dfd520f
Timestamp: 1713120767 Timestamp [UCT]: 2024-04-14 18:52:47 Age [y:d:h:m:s]: 01:291:08:15:56
Block: 1000506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466826 RingCT/type: yes/0
Extra: 01830d0c961058f4bb69c061d910febc1aa5cfe4c504eda8047e949a083dfd520f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62e6ecf43f848dfbd50399710c09fbc59d3f992513d63db18290e3392d776f83 0.600000000000 1461004 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": 1000516, "vin": [ { "gen": { "height": 1000506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62e6ecf43f848dfbd50399710c09fbc59d3f992513d63db18290e3392d776f83" } } ], "extra": [ 1, 131, 13, 12, 150, 16, 88, 244, 187, 105, 192, 97, 217, 16, 254, 188, 26, 165, 207, 228, 197, 4, 237, 168, 4, 126, 148, 154, 8, 61, 253, 82, 15, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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