Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 042f5a86476928090833091312f7a0d827e64eea13624ae441e9c66d4be450db

Tx prefix hash: f460d110c60a0d5e7da29d10cee1fabe34df94a3ecc2950fca450a670d6ad753
Tx public key: f2e52e1c95db5a3a6ea32e098cd0fe9e5ffbea8fc2cf7231d179aa6f92a1ba1d
Timestamp: 1734013352 Timestamp [UCT]: 2024-12-12 14:22:32 Age [y:d:h:m:s]: 00:111:08:41:27
Block: 1173641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79360 RingCT/type: yes/0
Extra: 01f2e52e1c95db5a3a6ea32e098cd0fe9e5ffbea8fc2cf7231d179aa6f92a1ba1d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a87dc743bfaeb4daa8ff3ae52846851ff3db7c2bec64b291c72dfb39fbc583e 0.600000000000 1659686 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": 1173651, "vin": [ { "gen": { "height": 1173641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a87dc743bfaeb4daa8ff3ae52846851ff3db7c2bec64b291c72dfb39fbc583e" } } ], "extra": [ 1, 242, 229, 46, 28, 149, 219, 90, 58, 110, 163, 46, 9, 140, 208, 254, 158, 95, 251, 234, 143, 194, 207, 114, 49, 209, 121, 170, 111, 146, 161, 186, 29, 2, 17, 0, 0, 0, 4, 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