Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b0dca1f0840bd61ab9a9e58fe3e5e7f67b992881cdccb9833f87ab9481c6d12

Tx prefix hash: b430ec349f04dcf933a619d9c08075b21b61e7f3695a5f638b40a5571a211d9e
Tx public key: f2f33097cbb21601d54ed39d1c08881a6149a2bf9c7463894ea0e14a8f91d98c
Timestamp: 1681257886 Timestamp [UCT]: 2023-04-12 00:04:46 Age [y:d:h:m:s]: 01:318:02:01:03
Block: 736594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488595 RingCT/type: yes/0
Extra: 01f2f33097cbb21601d54ed39d1c08881a6149a2bf9c7463894ea0e14a8f91d98c0211000000025029cbac000000000000000000

1 output(s) for total of 2.225146073000 dcy

stealth address amount amount idx
00: 0cb4a8d2f0d07537c4e6e0bf056a4f9ad3ef8eacb2ab3fa2fbc6835e7766057a 2.225146073000 1183049 of 0

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": 736604, "vin": [ { "gen": { "height": 736594 } } ], "vout": [ { "amount": 2225146073, "target": { "key": "0cb4a8d2f0d07537c4e6e0bf056a4f9ad3ef8eacb2ab3fa2fbc6835e7766057a" } } ], "extra": [ 1, 242, 243, 48, 151, 203, 178, 22, 1, 213, 78, 211, 157, 28, 8, 136, 26, 97, 73, 162, 191, 156, 116, 99, 137, 78, 160, 225, 74, 143, 145, 217, 140, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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