Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cf18c6f0bc99af740ee595eb1433a75e8ba8463c8c27a269e86f5dc7725bbad

Tx prefix hash: 8d0d4c8829b89cfa6201406a8fae1b8c4011a9423d1bae0cb32457d8646249a0
Tx public key: c6fce96ebf0f8adc5044e9fb67746e26130abe43003708e737d89ea9403fa6d7
Timestamp: 1733266533 Timestamp [UCT]: 2024-12-03 22:55:33 Age [y:d:h:m:s]: 00:023:04:47:23
Block: 1167444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16586 RingCT/type: yes/0
Extra: 01c6fce96ebf0f8adc5044e9fb67746e26130abe43003708e737d89ea9403fa6d70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16d5695591dac173254e2aa1c6d606b904d3b363b8f95b2272b67162f58b727f 0.600000000000 1653141 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": 1167454, "vin": [ { "gen": { "height": 1167444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16d5695591dac173254e2aa1c6d606b904d3b363b8f95b2272b67162f58b727f" } } ], "extra": [ 1, 198, 252, 233, 110, 191, 15, 138, 220, 80, 68, 233, 251, 103, 116, 110, 38, 19, 10, 190, 67, 0, 55, 8, 231, 55, 216, 158, 169, 64, 63, 166, 215, 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