Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f495909f27d8317125c4a57f3ffc43e6ee93e7adf22f096bbe78869a0af56c5e

Tx prefix hash: a543aaae363749b0afcae02408e577fbee3f0fbef2ad9bc5dacde36fbb3bc29a
Tx public key: 729b357d1c5cba12aace4f9432634363621ff9ea6c38eacf133d51f4df7a50e0
Timestamp: 1738281601 Timestamp [UCT]: 2025-01-31 00:00:01 Age [y:d:h:m:s]: 00:041:01:33:20
Block: 1208699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29375 RingCT/type: yes/0
Extra: 01729b357d1c5cba12aace4f9432634363621ff9ea6c38eacf133d51f4df7a50e0021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fe4072bd44e008424fe74a1ba1ad5b3ce45fc76e448d70928d2cf5cb34161e1 0.600000000000 1695432 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": 1208709, "vin": [ { "gen": { "height": 1208699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fe4072bd44e008424fe74a1ba1ad5b3ce45fc76e448d70928d2cf5cb34161e1" } } ], "extra": [ 1, 114, 155, 53, 125, 28, 92, 186, 18, 170, 206, 79, 148, 50, 99, 67, 99, 98, 31, 249, 234, 108, 56, 234, 207, 19, 61, 81, 244, 223, 122, 80, 224, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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