Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aca5548e3b0a94484205fbf14e41f244f0cfdf3cb72b4acff9b15d1868b9f508

Tx prefix hash: 2f896a696cd3fc1c310f3a7e8cc69518fbb7d30f9234e0495c5dfea8483553a5
Tx public key: 4fc875b0c27ee91cd59c951c3241c1c6c3afd844bc9058bb27798cb93ee2be97
Timestamp: 1736358284 Timestamp [UCT]: 2025-01-08 17:44:44 Age [y:d:h:m:s]: 00:316:13:06:26
Block: 1193035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223738 RingCT/type: yes/0
Extra: 014fc875b0c27ee91cd59c951c3241c1c6c3afd844bc9058bb27798cb93ee2be97021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e24026bc83bbe0594a69acb1e08a6f843c1e9fc09075cedf01ae6e178d53d12 0.600000000000 1679592 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": 1193045, "vin": [ { "gen": { "height": 1193035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e24026bc83bbe0594a69acb1e08a6f843c1e9fc09075cedf01ae6e178d53d12" } } ], "extra": [ 1, 79, 200, 117, 176, 194, 126, 233, 28, 213, 156, 149, 28, 50, 65, 193, 198, 195, 175, 216, 68, 188, 144, 88, 187, 39, 121, 140, 185, 62, 226, 190, 151, 2, 17, 0, 0, 0, 9, 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