Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e4e6fa93608da5f9337a31814155fef1cc5700437070b2ed36b54fba21502f3

Tx prefix hash: aa6adb70391ecfc91dc8564b49156951f86ec9cac7478b2981b03ad8fc30a3b0
Tx public key: 44272c1283e396acfad722ec44bf0d8c07a58beda7f3050a36cc3b2a0b292bee
Timestamp: 1696679083 Timestamp [UCT]: 2023-10-07 11:44:43 Age [y:d:h:m:s]: 01:186:21:00:12
Block: 864412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394611 RingCT/type: yes/0
Extra: 0144272c1283e396acfad722ec44bf0d8c07a58beda7f3050a36cc3b2a0b292bee02110000000136a45730000000000000000000

1 output(s) for total of 0.839158977000 dcy

stealth address amount amount idx
00: 9022c0a420ce4e976501633a7d4193ae915a6d247bd1f221c75a4d349d9dc692 0.839158977000 1318926 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": 864422, "vin": [ { "gen": { "height": 864412 } } ], "vout": [ { "amount": 839158977, "target": { "key": "9022c0a420ce4e976501633a7d4193ae915a6d247bd1f221c75a4d349d9dc692" } } ], "extra": [ 1, 68, 39, 44, 18, 131, 227, 150, 172, 250, 215, 34, 236, 68, 191, 13, 140, 7, 165, 139, 237, 167, 243, 5, 10, 54, 204, 59, 42, 11, 41, 43, 238, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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