Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4786fa24404cd156cb065df31050666f18c0ecec785a853cfa9f6a294713d387

Tx prefix hash: 2f5807b4661ab8c5cb29c8578b0df622632573f325965c24c18f5690327de7c0
Tx public key: f2b20468e0a5df19121a54dc1f126f4b9bde6072f8c3aba7d915270696ee5fb9
Timestamp: 1643439954 Timestamp [UCT]: 2022-01-29 07:05:54 Age [y:d:h:m:s]: 03:010:08:36:49
Block: 427606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 786573 RingCT/type: yes/0
Extra: 01f2b20468e0a5df19121a54dc1f126f4b9bde6072f8c3aba7d915270696ee5fb9021100000001bf7ee4e7000000000000000000

1 output(s) for total of 23.505209474000 dcy

stealth address amount amount idx
00: 099f7d30ee2d10bc55e59b7f6de72bdc306f5cb613d5a64bc8b001dccdb5ce0c 23.505209474000 836784 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": 427616, "vin": [ { "gen": { "height": 427606 } } ], "vout": [ { "amount": 23505209474, "target": { "key": "099f7d30ee2d10bc55e59b7f6de72bdc306f5cb613d5a64bc8b001dccdb5ce0c" } } ], "extra": [ 1, 242, 178, 4, 104, 224, 165, 223, 25, 18, 26, 84, 220, 31, 18, 111, 75, 155, 222, 96, 114, 248, 195, 171, 167, 217, 21, 39, 6, 150, 238, 95, 185, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 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