Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d3b4f232bb80a8133f3edc8d111f993765ef2861cdde7f53106233a6e6b1d6d

Tx prefix hash: 470178045036f7d5f0d2c778606e911222169f804c27bcabb90b15d66d773239
Tx public key: 94a7a1ebaad55316fd04783df9d7a25eac7763c6d9a303791c0290dd29ea31d5
Timestamp: 1735650007 Timestamp [UCT]: 2024-12-31 13:00:07 Age [y:d:h:m:s]: 01:028:22:00:48
Block: 1187168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278967 RingCT/type: yes/0
Extra: 0194a7a1ebaad55316fd04783df9d7a25eac7763c6d9a303791c0290dd29ea31d502110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75a3f3a76d7e9dd1f74a5365438b72c070d2eed279e554b9a5b60a9fc0cf2bed 0.600000000000 1673655 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": 1187178, "vin": [ { "gen": { "height": 1187168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75a3f3a76d7e9dd1f74a5365438b72c070d2eed279e554b9a5b60a9fc0cf2bed" } } ], "extra": [ 1, 148, 167, 161, 235, 170, 213, 83, 22, 253, 4, 120, 61, 249, 215, 162, 94, 172, 119, 99, 198, 217, 163, 3, 121, 28, 2, 144, 221, 41, 234, 49, 213, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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