Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75085ec8c684e31cae1b8b75ed0e21bfc62210cf70918343b6f9c6316b8576af

Tx prefix hash: 670c56994db6a523dc956adfe2cd7656625132024568436c2ffeabca6231c9d3
Tx public key: 722594e6b8245c6ee4b3d1e7710c0a80db85d61f912162d8ef4be9ea8cbc8aa3
Timestamp: 1727497538 Timestamp [UCT]: 2024-09-28 04:25:38 Age [y:d:h:m:s]: 00:116:19:24:25
Block: 1119717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83475 RingCT/type: yes/0
Extra: 01722594e6b8245c6ee4b3d1e7710c0a80db85d61f912162d8ef4be9ea8cbc8aa302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db2c6fad743e2daa0770c289bc175c1bb7a333c89f6964826f160e153e4cf1af 0.600000000000 1601378 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": 1119727, "vin": [ { "gen": { "height": 1119717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db2c6fad743e2daa0770c289bc175c1bb7a333c89f6964826f160e153e4cf1af" } } ], "extra": [ 1, 114, 37, 148, 230, 184, 36, 92, 110, 228, 179, 209, 231, 113, 12, 10, 128, 219, 133, 214, 31, 145, 33, 98, 216, 239, 75, 233, 234, 140, 188, 138, 163, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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