Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5182ffea7f766c17a71e816e7df2b48da6998b04b7ee107dceb170ab956b289e

Tx prefix hash: 0ce23f2b6eeadc7b4c10d4c601e7dd305090fb4206e54575a47f1ecec76bac86
Tx public key: bc306b364532531198f97b7dfcb7c0fc7f1b0151c32af6c234209ddd389c9fa9
Timestamp: 1733976656 Timestamp [UCT]: 2024-12-12 04:10:56 Age [y:d:h:m:s]: 00:192:07:22:32
Block: 1173342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137071 RingCT/type: yes/0
Extra: 01bc306b364532531198f97b7dfcb7c0fc7f1b0151c32af6c234209ddd389c9fa90211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9adc578dd02b551c044814b24314084d40078053c90d243d6d58bc436797bf2d 0.600000000000 1659353 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": 1173352, "vin": [ { "gen": { "height": 1173342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9adc578dd02b551c044814b24314084d40078053c90d243d6d58bc436797bf2d" } } ], "extra": [ 1, 188, 48, 107, 54, 69, 50, 83, 17, 152, 249, 123, 125, 252, 183, 192, 252, 127, 27, 1, 81, 195, 42, 246, 194, 52, 32, 157, 221, 56, 156, 159, 169, 2, 17, 0, 0, 0, 5, 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