Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb136d14a01097e3ba6c4245751d0e39f6322a53f32f58bdf800bd51fe78e1ca

Tx prefix hash: 0986c5e3b16347f675aa27f96cd084a940fa080a8db992e652570171420a0a2e
Tx public key: a54bcf688c2b96f1de820ec0142c77df282bb9b23e02f5be01e1d553ec9aaa63
Timestamp: 1735858568 Timestamp [UCT]: 2025-01-02 22:56:08 Age [y:d:h:m:s]: 00:168:02:43:00
Block: 1188900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119837 RingCT/type: yes/0
Extra: 01a54bcf688c2b96f1de820ec0142c77df282bb9b23e02f5be01e1d553ec9aaa630211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dce16ad0d5b02e7cfb58fdbbae26605d45c0b674f9279a98523f242a1f0bf0e7 0.600000000000 1675405 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": 1188910, "vin": [ { "gen": { "height": 1188900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dce16ad0d5b02e7cfb58fdbbae26605d45c0b674f9279a98523f242a1f0bf0e7" } } ], "extra": [ 1, 165, 75, 207, 104, 140, 43, 150, 241, 222, 130, 14, 192, 20, 44, 119, 223, 40, 43, 185, 178, 62, 2, 245, 190, 1, 225, 213, 83, 236, 154, 170, 99, 2, 17, 0, 0, 0, 2, 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