Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 052c55fe717e90a0ff636002cb8c2120b4ab752a3681c5d692e47357eb87bb6a

Tx prefix hash: bb477ada50aa2f12075318d9d1a873cf32ed17d82fd896b7fc6be79ff77208c6
Tx public key: fec3a80abd9298be9b68770d05636adb4d6bb322f94dd8492acf3bda4c45e3e7
Timestamp: 1731482852 Timestamp [UCT]: 2024-11-13 07:27:32 Age [y:d:h:m:s]: 00:141:12:51:32
Block: 1152653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100980 RingCT/type: yes/0
Extra: 01fec3a80abd9298be9b68770d05636adb4d6bb322f94dd8492acf3bda4c45e3e70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1987f5619ccea7b1dbf756b78ad37543287c3a8fd1147ecca56f25b2c3f2f521 0.600000000000 1638256 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": 1152663, "vin": [ { "gen": { "height": 1152653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1987f5619ccea7b1dbf756b78ad37543287c3a8fd1147ecca56f25b2c3f2f521" } } ], "extra": [ 1, 254, 195, 168, 10, 189, 146, 152, 190, 155, 104, 119, 13, 5, 99, 106, 219, 77, 107, 179, 34, 249, 77, 216, 73, 42, 207, 59, 218, 76, 69, 227, 231, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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