Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93e96145fe643170832d13d4d0f6323fcb3b38b12450a2f01843c36a2e3aa02d

Tx prefix hash: 64bc9749e5a18974d2f87d8a2b1ab723ff92fdfc29c8d1497459c84e28363683
Tx public key: 0db3d58b21794b9a845f86eb56ba7b4a69a1e85e89dfb13115f58fb2292513f0
Timestamp: 1709822794 Timestamp [UCT]: 2024-03-07 14:46:34 Age [y:d:h:m:s]: 01:014:11:35:20
Block: 973193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271327 RingCT/type: yes/0
Extra: 010db3d58b21794b9a845f86eb56ba7b4a69a1e85e89dfb13115f58fb2292513f00211000000100011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1298df9f96eae76bc146ed1786a6a598565e7ba54b2705fe26984817db257a09 0.600000000000 1433126 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": 973203, "vin": [ { "gen": { "height": 973193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1298df9f96eae76bc146ed1786a6a598565e7ba54b2705fe26984817db257a09" } } ], "extra": [ 1, 13, 179, 213, 139, 33, 121, 75, 154, 132, 95, 134, 235, 86, 186, 123, 74, 105, 161, 232, 94, 137, 223, 177, 49, 21, 245, 143, 178, 41, 37, 19, 240, 2, 17, 0, 0, 0, 16, 0, 17, 5, 91, 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