Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2636c7ed0c85a37852207f7fd11aa453f9e0378b11c6b5b5a821412e8187881c

Tx prefix hash: ffa41ea09c4cff60f2ac6bdfb22b8d9c3f5decfd955742c5d8fc78f44b73d113
Tx public key: bfe5323b5893318bd0c28526d67e78a4c180386df39166490532094867f0d813
Timestamp: 1725400217 Timestamp [UCT]: 2024-09-03 21:50:17 Age [y:d:h:m:s]: 00:081:20:09:07
Block: 1102330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58520 RingCT/type: yes/0
Extra: 01bfe5323b5893318bd0c28526d67e78a4c180386df39166490532094867f0d813021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60c3f59fdf25e642067dfd34f710e7429b6e97fb131d3c8cac7479ccc4feea2e 0.600000000000 1578725 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": 1102340, "vin": [ { "gen": { "height": 1102330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60c3f59fdf25e642067dfd34f710e7429b6e97fb131d3c8cac7479ccc4feea2e" } } ], "extra": [ 1, 191, 229, 50, 59, 88, 147, 49, 139, 208, 194, 133, 38, 214, 126, 120, 164, 193, 128, 56, 109, 243, 145, 102, 73, 5, 50, 9, 72, 103, 240, 216, 19, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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