Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c5b618c117c627a0c47cb5e98bb02c565bddf0e1e030ea00ff8bb82311ea8c4

Tx prefix hash: 145c11c546d6ad3363dcc2043670594b15674e3e5423b6108bbf0009018cf056
Tx public key: 3ce83f98681e24c366e56aab4e8f8fcc72c612a8f101379e20b1b2ba9bcafb40
Timestamp: 1713993908 Timestamp [UCT]: 2024-04-24 21:25:08 Age [y:d:h:m:s]: 00:248:01:39:45
Block: 1007761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177566 RingCT/type: yes/0
Extra: 013ce83f98681e24c366e56aab4e8f8fcc72c612a8f101379e20b1b2ba9bcafb4002110000000459dad3f5000000000000000000

1 output(s) for total of 0.615580000000 dcy

stealth address amount amount idx
00: 024affc52106e24cc70aa2addb8a03b96daed2f46b33ef1c43142ef7a1bd780f 0.615580000000 1469201 of 0

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": 1007771, "vin": [ { "gen": { "height": 1007761 } } ], "vout": [ { "amount": 615580000, "target": { "key": "024affc52106e24cc70aa2addb8a03b96daed2f46b33ef1c43142ef7a1bd780f" } } ], "extra": [ 1, 60, 232, 63, 152, 104, 30, 36, 195, 102, 229, 106, 171, 78, 143, 143, 204, 114, 198, 18, 168, 241, 1, 55, 158, 32, 177, 178, 186, 155, 202, 251, 64, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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