Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a589ae7cdc3796c43e6e7761d41e206d29dcb453efb75cc615f3b894a767ef9

Tx prefix hash: 8c574b8dccb0eeb3186090dece724576f770a510ac1db8ce04a58ae84723bb98
Tx public key: b1feeaf38139873f9a9f97ebdfe2a60b66c1dc6f1907644901857c22401463c2
Timestamp: 1705451243 Timestamp [UCT]: 2024-01-17 00:27:23 Age [y:d:h:m:s]: 01:309:01:17:50
Block: 936911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479710 RingCT/type: yes/0
Extra: 01b1feeaf38139873f9a9f97ebdfe2a60b66c1dc6f1907644901857c22401463c202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73d8ccc2a5c92b4cb1424259bd527f91699dfa3c4e1fef03dfe24932281a2ea2 0.600000000000 1394955 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": 936921, "vin": [ { "gen": { "height": 936911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73d8ccc2a5c92b4cb1424259bd527f91699dfa3c4e1fef03dfe24932281a2ea2" } } ], "extra": [ 1, 177, 254, 234, 243, 129, 57, 135, 63, 154, 159, 151, 235, 223, 226, 166, 11, 102, 193, 220, 111, 25, 7, 100, 73, 1, 133, 124, 34, 64, 20, 99, 194, 2, 17, 0, 0, 0, 3, 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