Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ffc1228a421ad36c85e807a2844cd7d02c9b8e1f7d7014631063ca50fe623ab

Tx prefix hash: 303881c2373bbaefcd91c2ea24dea7d30344e6507313ddd26ad04cc24bbfda8c
Tx public key: 92f7651c19fc17ea4dc6e542df6b6dbf3ec8ddb8765032cdb71da9a1c4bbdc11
Timestamp: 1736993334 Timestamp [UCT]: 2025-01-16 02:08:54 Age [y:d:h:m:s]: 00:152:17:59:35
Block: 1198288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108889 RingCT/type: yes/0
Extra: 0192f7651c19fc17ea4dc6e542df6b6dbf3ec8ddb8765032cdb71da9a1c4bbdc11021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77d0ccc9ca9b1660095dce7cdba9a5d1162670d303da334c7383ca364a04c52d 0.600000000000 1684911 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": 1198298, "vin": [ { "gen": { "height": 1198288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77d0ccc9ca9b1660095dce7cdba9a5d1162670d303da334c7383ca364a04c52d" } } ], "extra": [ 1, 146, 247, 101, 28, 25, 252, 23, 234, 77, 198, 229, 66, 223, 107, 109, 191, 62, 200, 221, 184, 118, 80, 50, 205, 183, 29, 169, 161, 196, 187, 220, 17, 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