Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f394cc4385bf2aa1af64909e19a67f4e48635912440f98d4d7a8ad42b2cbe1b1

Tx prefix hash: 924558a6f92ef142ec6a31236192887bde19c2776b32b40f42d60f60c62a9c0b
Tx public key: 8c78e7e7dc91331324ee68a7fcc2866c7e3fb383ce3336cd43a060fd8212b844
Timestamp: 1717431163 Timestamp [UCT]: 2024-06-03 16:12:43 Age [y:d:h:m:s]: 00:301:08:58:01
Block: 1036271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215365 RingCT/type: yes/0
Extra: 018c78e7e7dc91331324ee68a7fcc2866c7e3fb383ce3336cd43a060fd8212b8440211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35860db97b59ea865f34656d2ae50e39a3b9d4f26e962b4dc7442e5f668eecca 0.600000000000 1504796 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": 1036281, "vin": [ { "gen": { "height": 1036271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35860db97b59ea865f34656d2ae50e39a3b9d4f26e962b4dc7442e5f668eecca" } } ], "extra": [ 1, 140, 120, 231, 231, 220, 145, 51, 19, 36, 238, 104, 167, 252, 194, 134, 108, 126, 63, 179, 131, 206, 51, 54, 205, 67, 160, 96, 253, 130, 18, 184, 68, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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