Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31aa555213ca23dd3eb47f4f56ca76678c5016da08fb7799ec14dbbed29628b5

Tx prefix hash: 8ad70247bc048c58d4bfb6e9baeafe60fa0edc146dfce9b60d8f50db854cb5e0
Tx public key: 35f30b2a218e37666f95118c349e57ce26e422d227190a334e821d2b7f380742
Timestamp: 1701534704 Timestamp [UCT]: 2023-12-02 16:31:44 Age [y:d:h:m:s]: 01:049:12:54:46
Block: 904466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296749 RingCT/type: yes/0
Extra: 0135f30b2a218e37666f95118c349e57ce26e422d227190a334e821d2b7f38074202110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.618199511000 dcy

stealth address amount amount idx
00: c67e12eb551669c071205edf3c4ac513b5a50c75563ba6ea0f0d1435e99269a4 0.618199511000 1361223 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": 904476, "vin": [ { "gen": { "height": 904466 } } ], "vout": [ { "amount": 618199511, "target": { "key": "c67e12eb551669c071205edf3c4ac513b5a50c75563ba6ea0f0d1435e99269a4" } } ], "extra": [ 1, 53, 243, 11, 42, 33, 142, 55, 102, 111, 149, 17, 140, 52, 158, 87, 206, 38, 228, 34, 210, 39, 25, 10, 51, 78, 130, 29, 43, 127, 56, 7, 66, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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