Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb609ee82a6d1e3493124679d8dcd93eb2f99a8e365167de6b4393916c916c96

Tx prefix hash: cc20496737393c8526a45e91c879e06bdc2211a1f3d9f3a9038ac5ce59e52df1
Tx public key: 153d3b735f2e8ef675becf959a40bf6b6629d7069e84ae8ad88fa6e40d4aa969
Timestamp: 1735069079 Timestamp [UCT]: 2024-12-24 19:37:59 Age [y:d:h:m:s]: 00:099:05:48:40
Block: 1182376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70698 RingCT/type: yes/0
Extra: 01153d3b735f2e8ef675becf959a40bf6b6629d7069e84ae8ad88fa6e40d4aa9690211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13c6513abf9af10f15c91f480096f4a317adafb45d94e72c284199e2fb9fe686 0.600000000000 1668809 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": 1182386, "vin": [ { "gen": { "height": 1182376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13c6513abf9af10f15c91f480096f4a317adafb45d94e72c284199e2fb9fe686" } } ], "extra": [ 1, 21, 61, 59, 115, 95, 46, 142, 246, 117, 190, 207, 149, 154, 64, 191, 107, 102, 41, 215, 6, 158, 132, 174, 138, 216, 143, 166, 228, 13, 74, 169, 105, 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