Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 879c4bc2769101e7276428b03c4493b2f71c4ca7e70f84f090391dd7b32fae5c

Tx prefix hash: 48472983cbeb98dccd4c56e1420a96ddd51917a9d7dc8f394f3ca86b5fee6691
Tx public key: 74dced0d08d53fac992fc157e9ca5dbd42a5aa7850d2b7ea59b2efcb920e0af1
Timestamp: 1740922861 Timestamp [UCT]: 2025-03-02 13:41:01 Age [y:d:h:m:s]: 00:264:07:36:08
Block: 1230550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186664 RingCT/type: yes/0
Extra: 0174dced0d08d53fac992fc157e9ca5dbd42a5aa7850d2b7ea59b2efcb920e0af1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1bad0966413fe070415233688a6ae84a981b26aae85ac315da4374c6569a09b 0.600000000000 1717449 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": 1230560, "vin": [ { "gen": { "height": 1230550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1bad0966413fe070415233688a6ae84a981b26aae85ac315da4374c6569a09b" } } ], "extra": [ 1, 116, 220, 237, 13, 8, 213, 63, 172, 153, 47, 193, 87, 233, 202, 93, 189, 66, 165, 170, 120, 80, 210, 183, 234, 89, 178, 239, 203, 146, 14, 10, 241, 2, 17, 0, 0, 0, 2, 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