Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ca08b77953bdb52bb391411b3c27bbd5314314ce26d17f8f151f8679c2efe7

Tx prefix hash: 6035dab64687843d78dc2b2c462afb51d52090249245264b7f14db5817b54522
Tx public key: 20aa3e610d4b92a7509c7cf5dffd128f78e56e01174e1d93f839d3c3cf2b220a
Timestamp: 1704782471 Timestamp [UCT]: 2024-01-09 06:41:11 Age [y:d:h:m:s]: 01:080:18:42:39
Block: 931367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318852 RingCT/type: yes/0
Extra: 0120aa3e610d4b92a7509c7cf5dffd128f78e56e01174e1d93f839d3c3cf2b220a02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 369e88d8a0e73892eb078e84807bb7b230483ad6316de616b0062dd52595d0f3 0.600000000000 1389265 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": 931377, "vin": [ { "gen": { "height": 931367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "369e88d8a0e73892eb078e84807bb7b230483ad6316de616b0062dd52595d0f3" } } ], "extra": [ 1, 32, 170, 62, 97, 13, 75, 146, 167, 80, 156, 124, 245, 223, 253, 18, 143, 120, 229, 110, 1, 23, 78, 29, 147, 248, 57, 211, 195, 207, 43, 34, 10, 2, 17, 0, 0, 0, 6, 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