Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8ec02390c08281d61e18f87c4aa0950b6315a1bbebb6c81020b0be7f87b3fde

Tx prefix hash: dab0d48c38a3d7789c849f7224d26f92bf9e0f498d217af6bf9f77319b92603d
Tx public key: 63e38e8047200c003a99faf2728bfc087b6d0d9bc77ebbb7012f3f7ec539749c
Timestamp: 1725823254 Timestamp [UCT]: 2024-09-08 19:20:54 Age [y:d:h:m:s]: 00:234:01:11:01
Block: 1105839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167114 RingCT/type: yes/0
Extra: 0163e38e8047200c003a99faf2728bfc087b6d0d9bc77ebbb7012f3f7ec539749c02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdb2e8b33bf8ff3fd302a2fe3cc3815edae4219dbf31d6fd2e98cce42c2f32f5 0.600000000000 1583316 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": 1105849, "vin": [ { "gen": { "height": 1105839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdb2e8b33bf8ff3fd302a2fe3cc3815edae4219dbf31d6fd2e98cce42c2f32f5" } } ], "extra": [ 1, 99, 227, 142, 128, 71, 32, 12, 0, 58, 153, 250, 242, 114, 139, 252, 8, 123, 109, 13, 155, 199, 126, 187, 183, 1, 47, 63, 126, 197, 57, 116, 156, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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