Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cb69d11b45ac93ec52aa2caa38f1f57b9723fc1cf00f74f134ae287e37c385e

Tx prefix hash: 67575382125de8e91f16f0ae4c2714204c6537aec2deb7ac259ded373ceb57bb
Tx public key: 5535c79dcb048b4db25ed4ecc40df3ab86405a6acbf61fa98e4692f6c268ab1d
Timestamp: 1702717065 Timestamp [UCT]: 2023-12-16 08:57:45 Age [y:d:h:m:s]: 01:330:16:27:19
Block: 914272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495188 RingCT/type: yes/0
Extra: 015535c79dcb048b4db25ed4ecc40df3ab86405a6acbf61fa98e4692f6c268ab1d02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 333038e6fa99736759b9dfe05dbceb72129f226e1d7d411211080e3ac8c0c60c 0.600000000000 1371566 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": 914282, "vin": [ { "gen": { "height": 914272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "333038e6fa99736759b9dfe05dbceb72129f226e1d7d411211080e3ac8c0c60c" } } ], "extra": [ 1, 85, 53, 199, 157, 203, 4, 139, 77, 178, 94, 212, 236, 196, 13, 243, 171, 134, 64, 90, 106, 203, 246, 31, 169, 142, 70, 146, 246, 194, 104, 171, 29, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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