Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12fd094dca0c98e8a2987800fccf7a35e382a0127f32e733c556d56a6f1de570

Tx prefix hash: fd033ba15837524706ba7766d931695a6797eba56239d32a980b65bd6e3dc9cd
Tx public key: 827d99708cc2f6fd2507fafcb710996d902ae139855f27a0510a186b8ac06701
Timestamp: 1724921340 Timestamp [UCT]: 2024-08-29 08:49:00 Age [y:d:h:m:s]: 00:218:07:18:22
Block: 1098350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155885 RingCT/type: yes/0
Extra: 01827d99708cc2f6fd2507fafcb710996d902ae139855f27a0510a186b8ac0670102110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e9610c1b9ec17debed2763f79e5d1c23d20a1847f4ff5bddf4c4a79ba7b5b6e 0.600000000000 1574039 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": 1098360, "vin": [ { "gen": { "height": 1098350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e9610c1b9ec17debed2763f79e5d1c23d20a1847f4ff5bddf4c4a79ba7b5b6e" } } ], "extra": [ 1, 130, 125, 153, 112, 140, 194, 246, 253, 37, 7, 250, 252, 183, 16, 153, 109, 144, 42, 225, 57, 133, 95, 39, 160, 81, 10, 24, 107, 138, 192, 103, 1, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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