Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8784aa61b6b71dd434f1ba115de9e63d4eb5e13b5a672f7fd8dd2eba60e9dc6

Tx prefix hash: 35273535769ff3e6a36977ec4b0fc8aff33c2912cc83206d41fddf08559c4bd8
Tx public key: f61518a4a5e6bc31b1a51c5a6f53da9761aac87683f1403f6ab0a1fb4c7b78a5
Timestamp: 1674307417 Timestamp [UCT]: 2023-01-21 13:23:37 Age [y:d:h:m:s]: 01:356:20:03:28
Block: 679598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516050 RingCT/type: yes/0
Extra: 01f61518a4a5e6bc31b1a51c5a6f53da9761aac87683f1403f6ab0a1fb4c7b78a50211000000035029cbac000000000000000000

1 output(s) for total of 3.437238397000 dcy

stealth address amount amount idx
00: 836f8d13119626441eed60c8e2d9d6e847e71f013791c36614104491267e4b95 3.437238397000 1121601 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": 679608, "vin": [ { "gen": { "height": 679598 } } ], "vout": [ { "amount": 3437238397, "target": { "key": "836f8d13119626441eed60c8e2d9d6e847e71f013791c36614104491267e4b95" } } ], "extra": [ 1, 246, 21, 24, 164, 165, 230, 188, 49, 177, 165, 28, 90, 111, 83, 218, 151, 97, 170, 200, 118, 131, 241, 64, 63, 106, 176, 161, 251, 76, 123, 120, 165, 2, 17, 0, 0, 0, 3, 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