Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05edfd8d52b8c79bd8bad33da131b3899bbc5a46f748a4640b1f2333112e2ee0

Tx prefix hash: 865e8d1fb891398319e41a0022b4139fe94d64bc630374d650853264481ac680
Tx public key: 835239336156111ae87c70a0df0bb817499b1719f6c559f51bf2e34e0f1208ef
Timestamp: 1633172518 Timestamp [UCT]: 2021-10-02 11:01:58 Age [y:d:h:m:s]: 03:048:06:21:03
Block: 345127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 811401 RingCT/type: yes/0
Extra: 01835239336156111ae87c70a0df0bb817499b1719f6c559f51bf2e34e0f1208ef021100000001f60c5d7e000000000000000000

1 output(s) for total of 44.101301581000 dcy

stealth address amount amount idx
00: aa4da799a09f4463d0dabb941708b4d7ec208a6078d067aa6462d27fd457d6df 44.101301581000 707993 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": 345137, "vin": [ { "gen": { "height": 345127 } } ], "vout": [ { "amount": 44101301581, "target": { "key": "aa4da799a09f4463d0dabb941708b4d7ec208a6078d067aa6462d27fd457d6df" } } ], "extra": [ 1, 131, 82, 57, 51, 97, 86, 17, 26, 232, 124, 112, 160, 223, 11, 184, 23, 73, 155, 23, 25, 246, 197, 89, 245, 27, 242, 227, 78, 15, 18, 8, 239, 2, 17, 0, 0, 0, 1, 246, 12, 93, 126, 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