Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d405144357093ef18ef29bba2e5f844ef9f2ec231004d79e63e5406c7da63aa4

Tx prefix hash: b36bd6a8268c63d29704f667e40b1dbd9a42b658cf1c9ee35fd45ad43a64c819
Tx public key: ff3f12d5f9ed8b24e8140a60c3abaae186643445cdc0982bc1edf371bb470e45
Timestamp: 1703341175 Timestamp [UCT]: 2023-12-23 14:19:35 Age [y:d:h:m:s]: 01:174:20:56:10
Block: 919445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386050 RingCT/type: yes/0
Extra: 01ff3f12d5f9ed8b24e8140a60c3abaae186643445cdc0982bc1edf371bb470e4502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2f7dcfc2d2777e99f13329b68cae0c06e3ad08b82a539e9a31db061aae6a966 0.600000000000 1377117 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": 919455, "vin": [ { "gen": { "height": 919445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2f7dcfc2d2777e99f13329b68cae0c06e3ad08b82a539e9a31db061aae6a966" } } ], "extra": [ 1, 255, 63, 18, 213, 249, 237, 139, 36, 232, 20, 10, 96, 195, 171, 170, 225, 134, 100, 52, 69, 205, 192, 152, 43, 193, 237, 243, 113, 187, 71, 14, 69, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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