Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e685dff0d2cd26e6669c45196423d7e09dd197dbc2ae7c66285f702bb0f41a2

Tx prefix hash: 3c848b95c04145419793bc6cf13bc7989ad7c81ec6df1d1282b9401a625f60ef
Tx public key: e8adb02275f777d16fe4ef69abd557319bd88481cd6f4a55ad0a2792768507c2
Timestamp: 1590651132 Timestamp [UCT]: 2020-05-28 07:32:12 Age [y:d:h:m:s]: 05:014:15:09:13
Block: 103795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1198563 RingCT/type: yes/0
Extra: 01e8adb02275f777d16fe4ef69abd557319bd88481cd6f4a55ad0a2792768507c20211000003fa6ef253e7000000000000000000

1 output(s) for total of 278.025630803000 dcy

stealth address amount amount idx
00: 49df0042713d06388512e33e0eb529b036f56e9d017ab1d0a7fefc258349447c 278.025630803000 182042 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": 103805, "vin": [ { "gen": { "height": 103795 } } ], "vout": [ { "amount": 278025630803, "target": { "key": "49df0042713d06388512e33e0eb529b036f56e9d017ab1d0a7fefc258349447c" } } ], "extra": [ 1, 232, 173, 176, 34, 117, 247, 119, 209, 111, 228, 239, 105, 171, 213, 87, 49, 155, 216, 132, 129, 205, 111, 74, 85, 173, 10, 39, 146, 118, 133, 7, 194, 2, 17, 0, 0, 3, 250, 110, 242, 83, 231, 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