Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d357e7aacad0a837a9bd882f4b94097d1adb857bf0e5140d4e41f62137179f58

Tx prefix hash: ec87c396c6d872bc9308065c7ff38b64a3615f1757cf51259876bd25ea874e5e
Tx public key: ad428993990ca66fbbad3b0f94173bb7f3b75d662cc2dc773a8aaa902677193d
Timestamp: 1583753873 Timestamp [UCT]: 2020-03-09 11:37:53 Age [y:d:h:m:s]: 04:294:08:47:17
Block: 79483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105040 RingCT/type: yes/0
Extra: 01ad428993990ca66fbbad3b0f94173bb7f3b75d662cc2dc773a8aaa902677193d02110000000228db8c57000000000000000000

1 output(s) for total of 334.688366385000 dcy

stealth address amount amount idx
00: bcf47c6323171033e63d3fbcd9f512380b422e1f1a15bf3bc00ca1f9c385dbaf 334.688366385000 145343 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": 79493, "vin": [ { "gen": { "height": 79483 } } ], "vout": [ { "amount": 334688366385, "target": { "key": "bcf47c6323171033e63d3fbcd9f512380b422e1f1a15bf3bc00ca1f9c385dbaf" } } ], "extra": [ 1, 173, 66, 137, 147, 153, 12, 166, 111, 187, 173, 59, 15, 148, 23, 59, 183, 243, 183, 93, 102, 44, 194, 220, 119, 58, 138, 170, 144, 38, 119, 25, 61, 2, 17, 0, 0, 0, 2, 40, 219, 140, 87, 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