Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83a461739854ebbb038b9088aee5bf110420d781dda4232f2df1b2f7d234849a

Tx prefix hash: f7fd38ff668b639a0fb5438bae7e7b90775ba949694b198315a28558bb6c32e0
Tx public key: 6093f51c8ce4115334d3f01de5a7327e12f79a717cc31fa7799cacc936e9038a
Timestamp: 1651696893 Timestamp [UCT]: 2022-05-04 20:41:33 Age [y:d:h:m:s]: 03:184:08:54:12
Block: 494347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 910230 RingCT/type: yes/0
Extra: 016093f51c8ce4115334d3f01de5a7327e12f79a717cc31fa7799cacc936e9038a02110000001a4da16a3a000000000000000000

1 output(s) for total of 14.126136210000 dcy

stealth address amount amount idx
00: 16fe74f4f7d89c9a56998c0b9dd3e5e8dd24d61d7bdb7424a06dbe68997546a3 14.126136210000 917988 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": 494357, "vin": [ { "gen": { "height": 494347 } } ], "vout": [ { "amount": 14126136210, "target": { "key": "16fe74f4f7d89c9a56998c0b9dd3e5e8dd24d61d7bdb7424a06dbe68997546a3" } } ], "extra": [ 1, 96, 147, 245, 28, 140, 228, 17, 83, 52, 211, 240, 29, 229, 167, 50, 126, 18, 247, 154, 113, 124, 195, 31, 167, 121, 156, 172, 201, 54, 233, 3, 138, 2, 17, 0, 0, 0, 26, 77, 161, 106, 58, 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