Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b180c70d7e74fb235267da812c950f86fb6319d1fb142718e8024e3fcbcd08a

Tx prefix hash: 9ac64201b258722b5f8e3d2784388875f10d1ba4a0624ffb478431cf258c15e0
Tx public key: 1431e3392446ae2b1aeeabf9f3334271daaf02045e763ed854fde50eeaa4c3a9
Timestamp: 1706974784 Timestamp [UCT]: 2024-02-03 15:39:44 Age [y:d:h:m:s]: 01:275:15:04:25
Block: 949552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455769 RingCT/type: yes/0
Extra: 011431e3392446ae2b1aeeabf9f3334271daaf02045e763ed854fde50eeaa4c3a90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39edd694f504d05f83ae64760299d921a8fd58f7e41639b0251519e9bf3758ae 0.600000000000 1408082 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": 949562, "vin": [ { "gen": { "height": 949552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39edd694f504d05f83ae64760299d921a8fd58f7e41639b0251519e9bf3758ae" } } ], "extra": [ 1, 20, 49, 227, 57, 36, 70, 174, 43, 26, 238, 171, 249, 243, 51, 66, 113, 218, 175, 2, 4, 94, 118, 62, 216, 84, 253, 229, 14, 234, 164, 195, 169, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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