Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8378c0022b15b6bab20cbd272f1f493c997b68f042b9f6bbaeb50eeec5fd985a

Tx prefix hash: a694e807657cfcfffc0a10924e6624ded18b8997956f25d53a85c942b425fbc7
Tx public key: bab04792aa7c3e745b75f0bdcfc1d79c12aadab4f5fd0f3f56cdd7010a8327ba
Timestamp: 1735151384 Timestamp [UCT]: 2024-12-25 18:29:44 Age [y:d:h:m:s]: 00:172:16:59:04
Block: 1183052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123156 RingCT/type: yes/0
Extra: 01bab04792aa7c3e745b75f0bdcfc1d79c12aadab4f5fd0f3f56cdd7010a8327ba021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba1c4e7cf920e42a3ffdbea60891d14eb54baf0bff174724c449e90b24645ed7 0.600000000000 1669491 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": 1183062, "vin": [ { "gen": { "height": 1183052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba1c4e7cf920e42a3ffdbea60891d14eb54baf0bff174724c449e90b24645ed7" } } ], "extra": [ 1, 186, 176, 71, 146, 170, 124, 62, 116, 91, 117, 240, 189, 207, 193, 215, 156, 18, 170, 218, 180, 245, 253, 15, 63, 86, 205, 215, 1, 10, 131, 39, 186, 2, 17, 0, 0, 0, 8, 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