Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28a3ba88811d081f3cf972f9d386e17e82829138f503f6772c6eb739bca4a0ee

Tx prefix hash: ee41e7a59922fb9687f378cc9efc213f2f6f64eb076922aa5f1f7e5ab8718928
Tx public key: e213f297f696d67a078e7d23165d3b769861bee85fb6e5a95ac3fedde09ae3f5
Timestamp: 1730328639 Timestamp [UCT]: 2024-10-30 22:50:39 Age [y:d:h:m:s]: 00:151:20:41:20
Block: 1143096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108377 RingCT/type: yes/0
Extra: 01e213f297f696d67a078e7d23165d3b769861bee85fb6e5a95ac3fedde09ae3f5021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 370c976b71d1266cd03c72deec444ecfb2103150c5abac638b6dd70e6219198d 0.600000000000 1626959 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": 1143106, "vin": [ { "gen": { "height": 1143096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "370c976b71d1266cd03c72deec444ecfb2103150c5abac638b6dd70e6219198d" } } ], "extra": [ 1, 226, 19, 242, 151, 246, 150, 214, 122, 7, 142, 125, 35, 22, 93, 59, 118, 152, 97, 190, 232, 95, 182, 229, 169, 90, 195, 254, 221, 224, 154, 227, 245, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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