Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f35e99a20666460fb1be805e8850bdad00b16cda9443df0f2db09486196e28

Tx prefix hash: 16d690905b4ffd8eaf278a06e42a2fdc5b6d0b86fc42c4aa917f925369fd1cdc
Tx public key: a3e5cb8e43e1219d78fea8507a0db19ac46348444086e532cc8ea37459d641a1
Timestamp: 1661661190 Timestamp [UCT]: 2022-08-28 04:33:10 Age [y:d:h:m:s]: 02:210:22:21:35
Block: 575414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 671974 RingCT/type: yes/0
Extra: 01a3e5cb8e43e1219d78fea8507a0db19ac46348444086e532cc8ea37459d641a102110000000233af99f4000000000000000000

1 output(s) for total of 7.610525533000 dcy

stealth address amount amount idx
00: f62bd1a92548cd315f94236612efd8700e04e0965ad98638da5dce78037ca3b3 7.610525533000 1008750 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": 575424, "vin": [ { "gen": { "height": 575414 } } ], "vout": [ { "amount": 7610525533, "target": { "key": "f62bd1a92548cd315f94236612efd8700e04e0965ad98638da5dce78037ca3b3" } } ], "extra": [ 1, 163, 229, 203, 142, 67, 225, 33, 157, 120, 254, 168, 80, 122, 13, 177, 154, 196, 99, 72, 68, 64, 134, 229, 50, 204, 142, 163, 116, 89, 214, 65, 161, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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