Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ae31dbb391f61d95d1c4b519358f0e8022995b11929d16bd08ebdf958bed8a2

Tx prefix hash: 8941498a69f757d1a9b58418d6bd62c45d7d00114f9102054e4625b6068c46cf
Tx public key: 8f3b7e0a231be92900083e531e58bda19f6bd49165e0de12b9139f1a482311eb
Timestamp: 1719916226 Timestamp [UCT]: 2024-07-02 10:30:26 Age [y:d:h:m:s]: 01:141:11:29:51
Block: 1056862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359656 RingCT/type: yes/0
Extra: 018f3b7e0a231be92900083e531e58bda19f6bd49165e0de12b9139f1a482311eb021100000002ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8449b9edb0a24b11a992ad7546f1187a44c4a08f52d6748820a7ddb237324ef9 0.600000000000 1527291 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": 1056872, "vin": [ { "gen": { "height": 1056862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8449b9edb0a24b11a992ad7546f1187a44c4a08f52d6748820a7ddb237324ef9" } } ], "extra": [ 1, 143, 59, 126, 10, 35, 27, 233, 41, 0, 8, 62, 83, 30, 88, 189, 161, 159, 107, 212, 145, 101, 224, 222, 18, 185, 19, 159, 26, 72, 35, 17, 235, 2, 17, 0, 0, 0, 2, 221, 211, 219, 145, 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