Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361a02a5f85944fc58249ae1f91027708820eea1e3483a62419eb8a4b1b49714

Tx prefix hash: 4818559d22b253f29daf26862137a4a2987e194643bc4b78a6d22df1101bd1b5
Tx public key: a1de2c79d6f0718dc21ced2fbd71e63a4d4c5595ace16f54f1cc3acdefd3c880
Timestamp: 1740555153 Timestamp [UCT]: 2025-02-26 07:32:33 Age [y:d:h:m:s]: 00:267:00:28:56
Block: 1227497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188608 RingCT/type: yes/0
Extra: 01a1de2c79d6f0718dc21ced2fbd71e63a4d4c5595ace16f54f1cc3acdefd3c8800211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ae30fc4bb217d32ce982a81e955821a6de4741833e91a4d1ebd4f443e16fccf 0.600000000000 1714370 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": 1227507, "vin": [ { "gen": { "height": 1227497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ae30fc4bb217d32ce982a81e955821a6de4741833e91a4d1ebd4f443e16fccf" } } ], "extra": [ 1, 161, 222, 44, 121, 214, 240, 113, 141, 194, 28, 237, 47, 189, 113, 230, 58, 77, 76, 85, 149, 172, 225, 111, 84, 241, 204, 58, 205, 239, 211, 200, 128, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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