Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c85a64fc3ccde9047cf7abbab2ebe7ab4b3b7ff3969ec4e92b6ad6b025e215d9

Tx prefix hash: 3de78987636b84c869baf42c7784a3d4ab9b85650e47f5de2e5aa74de1eaf66c
Tx public key: 588cbe490ec94f3c6e215d323512192e6b73276e8afbf863de298f3d79133c22
Timestamp: 1670858567 Timestamp [UCT]: 2022-12-12 15:22:47 Age [y:d:h:m:s]: 02:028:15:07:23
Block: 651040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542377 RingCT/type: yes/0
Extra: 01588cbe490ec94f3c6e215d323512192e6b73276e8afbf863de298f3d79133c220211000000018b7b6602000000000000000000

1 output(s) for total of 4.273996926000 dcy

stealth address amount amount idx
00: b656625156514052c556d43a8af1ac1c90cbf6f033ad59b0f4bb6377d9dc8a5a 4.273996926000 1091441 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": 651050, "vin": [ { "gen": { "height": 651040 } } ], "vout": [ { "amount": 4273996926, "target": { "key": "b656625156514052c556d43a8af1ac1c90cbf6f033ad59b0f4bb6377d9dc8a5a" } } ], "extra": [ 1, 88, 140, 190, 73, 14, 201, 79, 60, 110, 33, 93, 50, 53, 18, 25, 46, 107, 115, 39, 110, 138, 251, 248, 99, 222, 41, 143, 61, 121, 19, 60, 34, 2, 17, 0, 0, 0, 1, 139, 123, 102, 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