Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3c9375be0d05dcf67333e4ba5e6e747988d5dcb53f5f594dc0a4698514725a4

Tx prefix hash: 74c071cbc78c91f0ac34ee3ad8a026145f7e436834a8cb48bbc832a7df3cd522
Tx public key: 62c72d08016b80a86f4ca406e8191a03761803c401f2dba19ba8bfdc5e21953d
Timestamp: 1737833451 Timestamp [UCT]: 2025-01-25 19:30:51 Age [y:d:h:m:s]: 00:324:17:56:48
Block: 1205213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229669 RingCT/type: yes/0
Extra: 0162c72d08016b80a86f4ca406e8191a03761803c401f2dba19ba8bfdc5e21953d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a0ed80f559ad0b86e2fbbfa49f7baeb35477ed33eba69711d7ff023f0ed4c14 0.600000000000 1691910 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": 1205223, "vin": [ { "gen": { "height": 1205213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a0ed80f559ad0b86e2fbbfa49f7baeb35477ed33eba69711d7ff023f0ed4c14" } } ], "extra": [ 1, 98, 199, 45, 8, 1, 107, 128, 168, 111, 76, 164, 6, 232, 25, 26, 3, 118, 24, 3, 196, 1, 242, 219, 161, 155, 168, 191, 220, 94, 33, 149, 61, 2, 17, 0, 0, 0, 4, 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