Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5236f9ffb60d9f02346add5eefc423da534c95e818cfb58c98f0cc3d905d6642

Tx prefix hash: 34bc9822bea22aba18ab45e96e30a7e2e132aa462dca8c69f6cfffae0d6a9552
Tx public key: 0cae6c707575fa219efc57d8ed1df81be8f9b4f0b586dc33e20cbbea1f958e8c
Timestamp: 1701491194 Timestamp [UCT]: 2023-12-02 04:26:34 Age [y:d:h:m:s]: 00:358:18:41:13
Block: 904101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256900 RingCT/type: yes/0
Extra: 010cae6c707575fa219efc57d8ed1df81be8f9b4f0b586dc33e20cbbea1f958e8c02110000000146113aa8000000000000000000

1 output(s) for total of 0.619923435000 dcy

stealth address amount amount idx
00: b8628ee6019ece3170df092f1168b1732ccf16925b6274cfe7b0d6682caa22d4 0.619923435000 1360808 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": 904111, "vin": [ { "gen": { "height": 904101 } } ], "vout": [ { "amount": 619923435, "target": { "key": "b8628ee6019ece3170df092f1168b1732ccf16925b6274cfe7b0d6682caa22d4" } } ], "extra": [ 1, 12, 174, 108, 112, 117, 117, 250, 33, 158, 252, 87, 216, 237, 29, 248, 27, 232, 249, 180, 240, 181, 134, 220, 51, 226, 12, 187, 234, 31, 149, 142, 140, 2, 17, 0, 0, 0, 1, 70, 17, 58, 168, 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