Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379a330a77498d1fbabde8b99a2eeb130dd8c54588b6fa460bce4dc665badb76

Tx prefix hash: e2865b9e5cbc8bd6632497bbc2f476e96f1c026c0876da9d6cf0b6a4d93fa59b
Tx public key: f04e46a1dc6aadc6e34a6a7225cfa3633de3ee8b337547322e67c60acc7fc9eb
Timestamp: 1663311943 Timestamp [UCT]: 2022-09-16 07:05:43 Age [y:d:h:m:s]: 02:121:00:47:57
Block: 589006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 608022 RingCT/type: yes/0
Extra: 01f04e46a1dc6aadc6e34a6a7225cfa3633de3ee8b337547322e67c60acc7fc9eb02110000000e75e3f0e9000000000000000000

1 output(s) for total of 6.860862093000 dcy

stealth address amount amount idx
00: ba1fa01962e23de4867e1bf6cfc8b1f9d3e90bb3d1c8f1740f9dfb90ca646d98 6.860862093000 1023269 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": 589016, "vin": [ { "gen": { "height": 589006 } } ], "vout": [ { "amount": 6860862093, "target": { "key": "ba1fa01962e23de4867e1bf6cfc8b1f9d3e90bb3d1c8f1740f9dfb90ca646d98" } } ], "extra": [ 1, 240, 78, 70, 161, 220, 106, 173, 198, 227, 74, 106, 114, 37, 207, 163, 99, 61, 227, 238, 139, 51, 117, 71, 50, 46, 103, 198, 10, 204, 127, 201, 235, 2, 17, 0, 0, 0, 14, 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