Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e78f26c2f1c4779ca4ae86e75d5ab0b043a12eaad7c4c9be1feb996efb5c925

Tx prefix hash: 53d9ac5496d5f5d3f3efa68e33edeac16ace478805976a9650fd8eec5fea0105
Tx public key: 91bb8b5794a0a8b3aa0d7de0da10637a837be4c5f649fb0e476d76f762b88701
Timestamp: 1578156489 Timestamp [UCT]: 2020-01-04 16:48:09 Age [y:d:h:m:s]: 04:363:12:02:39
Block: 38661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148982 RingCT/type: yes/0
Extra: 0191bb8b5794a0a8b3aa0d7de0da10637a837be4c5f649fb0e476d76f762b8870102110000001f4ac5aa02000000000000000000

1 output(s) for total of 456.983908355000 dcy

stealth address amount amount idx
00: 7f58fd2402c50ba75fb9d9f8644fb80c657c02be2f88e7f2bd4255e0ec08fa23 456.983908355000 66071 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": 38671, "vin": [ { "gen": { "height": 38661 } } ], "vout": [ { "amount": 456983908355, "target": { "key": "7f58fd2402c50ba75fb9d9f8644fb80c657c02be2f88e7f2bd4255e0ec08fa23" } } ], "extra": [ 1, 145, 187, 139, 87, 148, 160, 168, 179, 170, 13, 125, 224, 218, 16, 99, 122, 131, 123, 228, 197, 246, 73, 251, 14, 71, 109, 118, 247, 98, 184, 135, 1, 2, 17, 0, 0, 0, 31, 74, 197, 170, 2, 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