Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe1c4f406d4909ecca96fc768b89fa007e036df11165090b2710623b8fa4bed2

Tx prefix hash: ac458c25e858d1a2c0db042f84964fba951e2e64cfde0f4a6788f739f7441078
Tx public key: 7ba7aac12f6a1a236065bf6238dc7a4036c8fd0b9b4a10dfdd034f597478e1a1
Timestamp: 1749628836 Timestamp [UCT]: 2025-06-11 08:00:36 Age [y:d:h:m:s]: 00:154:01:14:37
Block: 1302623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107787 RingCT/type: yes/0
Extra: 017ba7aac12f6a1a236065bf6238dc7a4036c8fd0b9b4a10dfdd034f597478e1a1021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 194cdc8534a7a3093a4256dd0d66c6ad8a0702b267332434e32ccc719176170a 0.600000000000 1790194 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": 1302633, "vin": [ { "gen": { "height": 1302623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "194cdc8534a7a3093a4256dd0d66c6ad8a0702b267332434e32ccc719176170a" } } ], "extra": [ 1, 123, 167, 170, 193, 47, 106, 26, 35, 96, 101, 191, 98, 56, 220, 122, 64, 54, 200, 253, 11, 155, 74, 16, 223, 221, 3, 79, 89, 116, 120, 225, 161, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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