Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db1f35ace3d5544fe70e4366ad264777aae500f9b610bcb407d0c5740cb854cb

Tx prefix hash: 3bac40d418ce889cb955a799e329e33d0aebcec700c6d5f6aa44d4a43b23fea3
Tx public key: 13243f308197c1e9c87fcc331c437066a79e3373c503abe6ce9e563995b09bfe
Timestamp: 1737489105 Timestamp [UCT]: 2025-01-21 19:51:45 Age [y:d:h:m:s]: 00:147:16:31:11
Block: 1202351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105306 RingCT/type: yes/0
Extra: 0113243f308197c1e9c87fcc331c437066a79e3373c503abe6ce9e563995b09bfe02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c804e162e500e533895d6abfcadc92e18dc6caac766b91ceb910822e093064a 0.600000000000 1689014 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": 1202361, "vin": [ { "gen": { "height": 1202351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c804e162e500e533895d6abfcadc92e18dc6caac766b91ceb910822e093064a" } } ], "extra": [ 1, 19, 36, 63, 48, 129, 151, 193, 233, 200, 127, 204, 51, 28, 67, 112, 102, 167, 158, 51, 115, 197, 3, 171, 230, 206, 158, 86, 57, 149, 176, 155, 254, 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