Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3495432bd05a2e2f7d8646be6ad20466a7aa559b221b2b9606b81ca093de9cc

Tx prefix hash: ad07f61f87bc6f272ca773d9ef138f785785ab36b46520de6bfffea5125f7e99
Tx public key: 64c18567d1352df830f69d133a6ec7032c9f2efd9db04099fb6c27c765eccb41
Timestamp: 1719096213 Timestamp [UCT]: 2024-06-22 22:43:33 Age [y:d:h:m:s]: 00:320:23:28:01
Block: 1050043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229401 RingCT/type: yes/0
Extra: 0164c18567d1352df830f69d133a6ec7032c9f2efd9db04099fb6c27c765eccb41021100000004c5f9cfd0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10fb462ddd2898ac5428e304e5f6bd7ee9610e4cf82d4c8f31ad106222db450c 0.600000000000 1520194 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": 1050053, "vin": [ { "gen": { "height": 1050043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10fb462ddd2898ac5428e304e5f6bd7ee9610e4cf82d4c8f31ad106222db450c" } } ], "extra": [ 1, 100, 193, 133, 103, 209, 53, 45, 248, 48, 246, 157, 19, 58, 110, 199, 3, 44, 159, 46, 253, 157, 176, 64, 153, 251, 108, 39, 199, 101, 236, 203, 65, 2, 17, 0, 0, 0, 4, 197, 249, 207, 208, 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