Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b41b832548a3ab6b4a9241eb85d6f651132bd320c8d0bcb160d398e8ed8afeab

Tx prefix hash: 3d15c6dd8ceaf4c705cb4e85200625ae30ad7c5ecb5ad42dff9f833ed7e72e21
Tx public key: f2b772dee459c11ea879f85bd0f42478ace132106bdaa75e66df089d13c259cf
Timestamp: 1742187306 Timestamp [UCT]: 2025-03-17 04:55:06 Age [y:d:h:m:s]: 00:297:01:58:02
Block: 1241036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210129 RingCT/type: yes/0
Extra: 01f2b772dee459c11ea879f85bd0f42478ace132106bdaa75e66df089d13c259cf021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a41829f17699ffc80e3046c38a03aa5d934e9e9e4b5f89d099ab76510e30c5f 0.600000000000 1728009 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": 1241046, "vin": [ { "gen": { "height": 1241036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a41829f17699ffc80e3046c38a03aa5d934e9e9e4b5f89d099ab76510e30c5f" } } ], "extra": [ 1, 242, 183, 114, 222, 228, 89, 193, 30, 168, 121, 248, 91, 208, 244, 36, 120, 172, 225, 50, 16, 107, 218, 167, 94, 102, 223, 8, 157, 19, 194, 89, 207, 2, 17, 0, 0, 0, 6, 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