Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3474cf84fe815de7908f4bd03b7a70ccf2e1b3409c3b78ba5ff4e8c1b872cb95

Tx prefix hash: 6b6b3e787c61e5ddf4af926d44d41fecc04935c3c79e2a4e8b8335c5aed284ee
Tx public key: d41e57f29ad77da1110610b8508706f115df8096a6a035ed19a02e5874dd3b2f
Timestamp: 1696680963 Timestamp [UCT]: 2023-10-07 12:16:03 Age [y:d:h:m:s]: 01:203:10:47:44
Block: 864428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406467 RingCT/type: yes/0
Extra: 01d41e57f29ad77da1110610b8508706f115df8096a6a035ed19a02e5874dd3b2f02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.839056547000 dcy

stealth address amount amount idx
00: 5aab41baae34f95c79f0c3291df3c5e49b53fd3fe5f3427dbce0689a4079b1d1 0.839056547000 1318942 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": 864438, "vin": [ { "gen": { "height": 864428 } } ], "vout": [ { "amount": 839056547, "target": { "key": "5aab41baae34f95c79f0c3291df3c5e49b53fd3fe5f3427dbce0689a4079b1d1" } } ], "extra": [ 1, 212, 30, 87, 242, 154, 215, 125, 161, 17, 6, 16, 184, 80, 135, 6, 241, 21, 223, 128, 150, 166, 160, 53, 237, 25, 160, 46, 88, 116, 221, 59, 47, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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