Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b767a2f9e16ab8d4c35c0770dd2889c69f082164110d09d47eb67cff56d72d77

Tx prefix hash: bead16777590b201d1cced10642aa09e59d1ba334393caafdf305c6546b1eb18
Tx public key: a079bee890e8b638fe5fc672de60f66dd667e796e9fb2eaf6f4048c065f5d37f
Timestamp: 1634694430 Timestamp [UCT]: 2021-10-20 01:47:10 Age [y:d:h:m:s]: 03:193:23:45:27
Block: 356543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 916561 RingCT/type: yes/0
Extra: 01a079bee890e8b638fe5fc672de60f66dd667e796e9fb2eaf6f4048c065f5d37f02110000001436fe6557000000000000000000

1 output(s) for total of 40.422711959000 dcy

stealth address amount amount idx
00: cc57736847fc2aca600e91be57a887f8b86e8b46a7897d89254aa58e28b3ade1 40.422711959000 727419 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": 356553, "vin": [ { "gen": { "height": 356543 } } ], "vout": [ { "amount": 40422711959, "target": { "key": "cc57736847fc2aca600e91be57a887f8b86e8b46a7897d89254aa58e28b3ade1" } } ], "extra": [ 1, 160, 121, 190, 232, 144, 232, 182, 56, 254, 95, 198, 114, 222, 96, 246, 109, 214, 103, 231, 150, 233, 251, 46, 175, 111, 64, 72, 192, 101, 245, 211, 127, 2, 17, 0, 0, 0, 20, 54, 254, 101, 87, 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